Meta file system for big data

ABSTRACT

A computer implemented method, system, and apparatus for modeling a Big Data dataset, the method comprising creating non-specific representations of the Big Data dataset by representing, as objects in a computer model, non-specific representations including metaInformation, DataSet, BigData and Properties representations, and creating non-specific representations of mapping of the Big Data by representing, as objects in a computer model, non-specific representations including User representations and marker representations, where the user representations are mapped to one or more marker representations and the marker representations are matched to one or more elements of the Big Data dataset.

A portion of the disclosure of this patent document may contain commandformats and other computer language listings, all of which are subjectto copyright protection. The copyright owner has no objection to thefacsimile reproduction by anyone of the patent document or the patentdisclosure, as it appears in the Patent and Trademark Office patent fileor records, but otherwise reserves all copyright rights whatsoever.

RELATED APPLICATIONS

This application is related to co-pending US Patent Application, filedeven date, Ser. No. 13/290,858 entitled “GENOME BIG DATA INDEXING,”which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

This invention relates to Big Data.

BACKGROUND

The amount of data in our world has been exploding. Companies capturetrillions of bytes of information about their customers, suppliers, andoperations, and millions of networked sensors are being embedded in thephysical world in devices such as mobile phones and automobiles,sensing, creating, and communicating data. Multimedia and individualswith smartphones and on social network sites will continue to fuelexponential growth. Yet, the impact this growing amount of data willhave is unclear.

SUMMARY

A computer implemented method, system, and apparatus for modeling a BigData dataset, the method comprising creating non-specificrepresentations of the Big Data dataset by representing, as objects in acomputer model, non-specific representations including metaInformation,DataSet, BigData and Properties representations, and creatingnon-specific representations of mapping of the Big Data by representing,as objects in a computer model, non-specific representations includingUser representations and marker representations, where the userrepresentations are mapped to one or more marker representations and themarker representations are matched to one or more elements of the BigData dataset.

DESCRIPTION OF DRAWINGS

Objects, features, and advantages of embodiments disclosed herein may bebetter understood by referring to the following description inconjunction with the accompanying drawings. The drawings are not meantto limit the scope of the claims included herewith. For clarity, notevery element may be labeled in every figure. The drawings are notnecessarily to scale, emphasis instead being placed upon illustratingembodiments, principles, and concepts. Thus, features and advantages ofthe present disclosure will become more apparent from the followingdetailed description of exemplary embodiments thereof taken inconjunction with the accompanying drawings in which:

FIG. 1 is a simplified illustration of a model representation of BigData, in accordance with an embodiment of the present disclosure;

FIG. 2 is a simplified illustration of a model representation ofMetaData classification for Big Data, in accordance with an embodimentof the present disclosure;

FIG. 3 is a further simplified illustration of a model representation ofmetadata information for Big Data, in accordance with an embodiment ofthe present disclosure;

FIG. 4 is a simplified illustration of a model representation oftransforming unstructured data to structured data, in accordance with anembodiment of the present disclosure;

FIG. 5 is a simplified illustration of a model representation ofenabling a representation of both unstructured and structured data, inaccordance with an embodiment of the present disclosure;

FIG. 6 is a simplified method for creating metadata markers, inaccordance with an embodiment of the present disclosure;

FIG. 7 is a simplified illustration of a model representation ofmetadata mapped across an informational plane, a file plane, an objectstore plane, and a block plane, in accordance with an embodiment of thepresent disclosure;

FIG. 8 is a simplified method for creating and populating an IMM model,in accordance with an embodiment of the present disclosure;

FIG. 9 is a simplified illustration of a model representation ofmetadata in an IMM plane mapped to file systems, an object store plane,and a block plane, in accordance with an embodiment of the presentdisclosure;

FIG. 10 is a simplified illustration of a model representation of a datamodel for metadata, in accordance with an embodiment of the presentdisclosure;

FIG. 11 is a simplified illustration of a model representation of aConnecting to storage network industry association (SNIA) via refinedrelationships, in accordance with an embodiment of the presentdisclosure;

FIG. 12 is a simplified illustration of a model representation of ametadata markers and properties, in accordance with an embodiment of thepresent disclosure;

FIG. 13 is a simplified illustration of a model representation of asample user maker cluster pairs in respect to the data model, inaccordance with an embodiment of the present disclosure;

FIG. 14 is a simplified illustration of a model representation ofconnecting domains via an iMM model mapping, in accordance with anembodiment of the present disclosure;

FIG. 15 is a simplified illustration of a model representation of asemantic domain view in a bioinformatics project, in accordance with anembodiment of the present disclosure;

FIG. 16 is a simplified illustration of a model representation of a userview in a bioinformatics project, in accordance with an embodiment ofthe present disclosure;

FIG. 17 is a simplified alternative illustration of a modelrepresentation of a marker view in a bioinformatics project, inaccordance with an embodiment of the present disclosure;

FIG. 18 is a simplified further illustration of a model representationof a marker view in a bioinformatics project, in accordance with anembodiment of the present disclosure;

FIG. 19 is a simplified illustration of a model representation of anexample marker view in a bioinformatics project, in accordance with anembodiment of the present disclosure;

FIG. 20 is a simplified illustration of a chart denoting performancecharacteristics of storage mediums, in accordance with an embodiment ofthe present disclosure;

FIG. 21 is a simplified illustration of meshed planes of abstractionwith two index planes and a generation plane, in accordance with anembodiment of the present disclosure;

FIG. 22 is a simplified method for distributing and analyzing Big Data,in accordance with an embodiment of the present disclosure;

FIG. 23 is a simplified illustration of sequences, keys anddistributions, in accordance with an embodiment of the presentdisclosure;

FIG. 24 is a simplified method for distributing and analyzing Big Datafor BioInformatics, in accordance with an embodiment of the presentdisclosure;

FIG. 25 is an alternative simplified method for distributing andanalyzing Big Data for Bio Informatics, in accordance with an embodimentof the present disclosure;

FIG. 26 is an example of an embodiment of an apparatus that may utilizethe techniques described herein, in accordance with an embodiment of thepresent disclosure; and

FIG. 27 is an example of an embodiment of a method embodied on acomputer readable storage medium that may utilize the techniquesdescribed herein, in accordance with an embodiment of the presentinvention.

DETAILED DESCRIPTION

Typically, a file system and a storage device communicate through anetwork or other connection. Generally, the file system or file serverwould request data from the storage device and there would be latency ingetting the data from the storage device in the transportation mediumfrom the storage device to the file system, delay in accessing the dataon the data storage device, and delay and performing calculation on thedata at the file system or server. Conventional techniques havegenerally focused on making more of the information readily available atthe file server, or performing calculations at the storage device toenable less data to be transferred to the file system or server.However, conventional techniques have not been able to remove the needto bring information to the file server or system. Further, conventiontechniques often leverage disk or platter based storage, where data isstored in a sequential manner, which may require the sequence be read inorder to access data in the middle of the sequence.

In an embodiment, the current disclosure enables management of smallfiles where the content may come from few transactions or a segment ofvoluminous data. In certain embodiments, a file system may use modeledBig Data and optimize the information to a meta data level, so thatmillions of analyses may be done in efficient way. In some embodiments,a file system may keep track of modeled Big Data and provides enoughinformation as a function to business units. In further embodiments, themeta data file system may keep track of file access, usage and purposeto help IT organizations to charge back billing. In certain embodiments,the current disclosure may enable the use of Flash storage to enablequick access to metadata. In some embodiments, Flash storage may providea matrixed or instant type access to data without having to read throughunrelated sequence of data. In further embodiments, the currentdisclosure may remove the need to transfer information from the datastorage to the request by leveraging a metadata map with the request toprovide the necessary information.

In certain embodiments, a Meta File System for transactions andvoluminous data may help connect IT, business units and customers. In atleast one embodiment, the current disclosure may use the meta datamodels for big data, specification and examples for building the metafile systems for transactions and volumes of data, subscription,functions and algorithms to define meta information for the new filesystem, and charge back and other utility functions that help IT toprovide efficient and agile big data clouds.

Generally, the amount of data capture has grown in every area of globaleconomy. Normally, companies are churning out increasing amounts oftransactional data, capturing trillions of bytes of information abouttheir customers, suppliers, and operations. Conventionally, millions ofnetworked sensors embedded in the physical world in devices such asmobile phones, smart energy meters, automobiles, and industrial machinescreate data that is recorded and stored. Usually, as companies andorganizations generate a tremendous amount of digital data that arecreated as a by-product of their activities. Often, enterprises may becollecting data with greater granularity and frequency, capturing everycustomer transaction, attaching more personal information, and alsocollecting more information about consumer behavior in many differentenvironments. Usually, this activity increases the need for more storageand analytical capacity.

Typically, social media sites, smartphones, and other consumer devicesincluding PCs and laptops have allowed billions of individuals aroundthe world to contribute to the amount of data available. Normally,consumers communicate, browse, buy, share, and search creating largeamounts of consumer data. However, conventional techniques are not ableto monitor or analyze this “Big Data.” Generally, conventional modelingtechniques do not accommodate for or do not model the properties thatdefine Big Data. For example, conventional techniques may not be able toperform analysis on Big Data because of the sheer number and size oftransaction that would be necessary to perform the analysis. As well,conventional techniques may consider elements as attributes of the datawhen, to properly represent the Big Data these “attributes” may need tobe considered as properties of the Big Data.

In some embodiments, “Big Data” may refer to a dataset that has a size,volume, analytical requirements, or structure demands larger thantypical software tools can capture, store, manage, and analyze. Incertain embodiments, “Big Data” may refer to a dataset that has acombination of attributes, such as size, volume, structure, oranalytical requirements, with which typical software tools may not beable to work. In most embodiments, big data is not defined in terms ofbeing larger than a certain number of terabytes rather, as technologyadvances over time, the size of datasets that qualify as big data mayalso increase.

In further embodiments, the definition of “Big Data” may vary by sectoror industry, depending on what kinds of software tools are commonlyavailable and what sizes of datasets are common in a particularindustry. Big Data may refer to data from Digital Pathology, data fromseismological surveys, data from the financial industry, and other typesof data sets that are generally too large, for example in size or numberof transactions, to be modeled an analyzed with conventional techniques.

Typically, organizations and business units share IT services, which mayresult in the creation of Big Data. Generally, the network, apps, andservers are shared and/or dedicated in many instances. Usually, of cloudand Big Data models and analytic platforms provide opportunities for thestorage business. However, conventional file sizes vary depending on theverticals, domains and type of data. Conventionally solutions provide agood infrastructure to host files that are large in size, but not forsmaller files.

Generally, the world has structured, semi-structured, unstructured andmulti-structured information. Typically, some companies, such as Oracle,have explored the structured world, providing integrated systems addressin-memory real-time analytics of structured information. Conventionally,to deal with unstructured information, these companies may use MassiveParallel Processing (MPP) and Hadoop technologies to process andtransform information that is not structured into structured informationand store the now structured data. However, conventional techniques thatconvert unstructured data to structured data lose fidelity from the dataset, fidelity that may important to examining the data and this loss offidelity may not be reconstructed or it may be expensive to reconstructthe information from the structured data.

For example, using conventional techniques it may be expensive toretrieve information that resides “inside” (random location) a file, asit needs to be read sequentially until the information is found. Usingthe conventional techniques, once the information is found, it may behard to keep track of where the information is, requiring a search everytime. Typically, files and unstructured information forces/imposessequential rational, access, and analytical patterns, uncharacteristicof today's world, which may be mashed up, connected, where all the datais shared

Another convention problem with Big Data may be that users are exposedto multiple file systems. Generally, each file system has a differentinterface and the tools to navigate files are specific to the filesystem and cannot be leveraged on another file system. Usually, eachtool/application organizes information differently. Typically, the waysto organize information are poor and lack in contextual and semanticinformation. Conventionally, the high volume of big data and small data,i.e. the sheer number of files (order of thousands), makes it hard to“manage” and “organize” the files in a way that can be easily consumed.Traditional directory navigation tools may not be helpful useless, asthey were designed to browse directories containing tens of files, nothundreds or thousands.

Generally, typical single hierarchical structures may not adequate torepresent complex relationships (links) between files. Conventionally,content rich files may be organized in many different wayssimultaneously; relationships between files typically form a mash, asopposed to a hierarchy. Traditional mechanisms focus on administrativeproperties of the files, and do not capture “semantics” or “contextual”information such as administrative properties: owner, date, format,size, semantic properties: key words contained in the file, other filesreferenced by the file, contextual properties: application and/oroperation that generated the file.

In certain embodiments, the current disclosure may enable a semanticallyor contextual map or graph, which may provide the user with informationwithout needing to query the data set. In some embodiments, the currentdisclosure may enable a Viewer and Role, <Viewer, Role> for a Big Dataset, where not all data in the Big Data may be relevant to each Viewer.In some embodiments, a small percentage of the Big Data may be relevantfor a single <viewer, role> pair. In other embodiments, not all the datathat is relevant to one <viewer, role> may be relevant to other pairs.In at least some embodiments, each group or cluster of <viewer, role>pairs may be interested in a different subset of the data or interestedin different aspects of the data.

In certain embodiments, the current disclosure may decouple content froma file system (FS) structure and enable one file to be shared and viewedby multiple file systems and multiple users. In at least one embodiment,the current disclosure may enable information to be abstracted orharvested from the content of the file that may not otherwise bycaptured by the underlying FS. In other embodiments, knowledge may beinferred or learned from the information harvested and form the contentof the file, where previously such knowledge may not have been obtainedautomatically or preserved.

Generally, Big Data is Multi Structured and may be conventionallystored, analyzed and managed each type of information in a number ofdifferent ways. In some embodiments, structured data may be stored inBlock based, SQL, and RDMS type databases. In other embodiments,semi-structured data may be stored in XML Data Files, in File Basedsystems, and in Hadoop Map Reduce. In further embodiments,quasi-structured data may be data containing some inconsistencies indata values and formats, e.g., Web click-stream data. In someembodiments, unstructured data may be text documents that could besubject to analytics over text or numbers such as file based data,Hadoop MapReduce, and HDFS data. In other embodiments, unstructured datamay be images and video such as file based data, and data streamlinedwith technologies such as MapReduce, or Scale Out NAS data. Typically,it may be difficult to process information stored in all differentformats, cross-analyze content, or visualize and gain insight into theimportant information spread all over the different formats;

Generally, storing data using conventional techniques results in a lossof Intermediate Results. Conventionally, MapReduce technologies offer away to distribute processing of information (map) and then combine itinto a result (reduce). However, these conventionally technologiesusually compute such that the data in the intermediate steps is oftendiscarded. Thus, in these conventionally techniques, when theinformation is required again, it is often computed again. In someembodiments of the current disclosure, the same intermediate information(map) may be “reduced” in many different ways when the intermediateinformation may offer insight that maybe extremely valuable as anabstract, pre-processed way of looking into the information;

Conventionally, there is not a way to provide cross-correlation acrossdifferent perspectives. Generally, it may be difficult to processinformation stored in all different formats, cross-analyze content, orvisualize and gain insight into the important information spread allover the different formats. As used herein, the following may be usefulin understanding the following term:

Data may be any collection of bits. An Information System may be asystem that provides and support a structure to create, update, delete,store, organize and manage data. Examples of Information Systems may beFile Systems, Object Stores, Database Systems, and a Block. A Marker,also referred to here as meta-information, may be a piece ofdata/information which can be associated (connected) to data. A MarkerCluster may be a set of markers. A Mark may be a property of a Data. AMaker may consist of a set of Marks. A set of Marks may define a Marker

A user may be a <Person, Role>, where a user is a pair identifying aperson and one of his roles. A person may have/assume different roles.Security and access privileges to Markers may be granted to users, andmaybe derived and verified in the context of the privileges assigned toPeople and their Roles. Users may be connected to Markers and MarkerClusters

Modeling Big Data

Referring to FIG. 1, this figure illustrates an exemplary abstract modelfor Big Data in accordance with the current disclosure. The classes,objects, and representations shown in the model may be an extension ofknown distributed system models, such as the EMC/Smarts CommonInformation Model (ICIM), or similarly defined or pre-existing CIM-basedmodel and adapted for the environmental distributed system, as will bediscussed. EMC and SMARTS are trademarks of EMC Corporation, Inc.,having a principle place of business in Hopkinton, Ma, USA. Thisexemplary model is an extension of the DMTF/SMI model. Model basedsystem representation is discussed in commonly-owned U.S. patentapplication Ser. No. 11/263,689, filed Nov. 1, 2005, and Ser. No.11/034,192, filed Jan. 12, 2005 and U.S. Pat. Nos. 5,528,516; 5,661,668;6,249,755 and 6,868,367, and 7,003,433, the contents of all of which arehereby incorporated by reference. An example of a Big Data Set may befound in commonly-owned U.S. patent application Ser. No. 12/977,680,filed Dec. 23, 2010, entitled “INFORMATION AWARE DIFFERENTIAL STRIPING”the contents of which are hereby incorporated by reference. An exampleof modeling Big Data Set may be found in commonly-owned U.S. patentapplication Ser. No. 12/977,680, filed Sep. 30, 2011, entitled “MODELINGBIG DATA” the contents of which are hereby incorporated by reference. Anexample of analyzing Big Data Set may be found in commonly-owned U.S.patent application Ser. No. 12/977,680, filed Sep. 30, 2011, entitled“ANALYZING BIG DATA” the contents of which are hereby incorporated byreference.

Generally, referred-to US Patents and patent applications disclosemodeling of distributed systems by defining a plurality of networkconfiguration non-specific representations of types of components(elements or devices) managed in a network and a plurality of networkconfiguration non-specific representations of relations among the typesof managed components and problems and symptoms associated with thecomponents and the relationships. The configuration non-specificrepresentations of components and relationships may be correlated with aspecific Big Data set for which the associated managed componentproblems may propagate through the analyzed system and the symptomsassociated with the data set may be detected an analyzed. An analysis ofthe symptoms detected may be performed to determine the root cause—i.e.,the source of the problem—of the observed symptoms. Other analysis, suchas impact, fault detection, fault monitoring, performance, congestion,connectivity, interface failure, in addition to root-cause analysis, maysimilarly be performed based on the model principles described herein.

Refer again to the example embodiment of FIG. 1. FIG. 1 illustrates anexample embodiment of a data hierarchy for a model that may be used tomodel Big Data. In this embodiment, a data set may have one or moreproperties that are bigger in size or volume or analytical propertiesthat may normally be modeled. In FIG. 1, DataSet 105 Contains 115 BigData 125 and MetaInformation 110 Represents 120 Big Data 125. MetaInformation 110 may be classes or objects that hold key attributes ofBig Data 125 which may be used for a quick analysis.

Big Data 125 may also have Properties 135 which Belong To 130 Big Data135. Properties 135 may contain properties that are Analytical 140,Volume 145, Size 150, and Structural 155. In some embodiments, there maybe an analytical property, which may be a class or object that containTransactional Properties or Quantitative/Numerical Properties orIteratative or HPC properties to the purpose of analytics and reporting.In certain embodiments, there may be a volume property class or objectwhich may contain the information of List or Hierarchical or Sequentialor Mash or Blogs. Big Data 125 may be Analyzed On 160 Resource Pool 165.Resource Pool 165 may represent the available computing, storage andnetwork resources, physical and virtual, for the purpose of analysis,storage, and transfer of the analyzed information.

Refer now to the example embodiment of FIG. 2. FIG. 2 illustrates someobjects and representations that may be useful in modeling big data.Meta Information 205 may be Classified As 210 Meta Data Classification215 which may be Contained In 220 Metadata Folder 230, which Contains235 metadata content 240. Metadata classification 215 may be Classifiedby 225 Metadata Content 240.

In some embodiments, Meta Information may have a set of key attributes.In some embodiments, the set may include some or all of the attributesof sources, creation time, file format, blocks, object store,DataBase-Type, Linked-Metadata-List, growth rate, last used,analysis-Type-List, analysis-Policy-List, compute-Resource-Used.

Refer now to the example embodiment of FIG. 3. FIG. 3 illustrates someobjects and representations that may be useful in modeling big data. InFIG. 3, MetaInformation 305 may be Part Of 310 Syntax 315 and Semantic320 and may be a class or object that holds the key information aboutthe big data. Syntax 315 may be a class or object that represents thesyntactic meta information of the big data. In FIG. 3, Syntax 315 may beComposed Of 325 Format 335. In the example embodiment of FIG. 3, Format335 may be a class or object which represents the format in which datais formatted. In the embodiment of FIG. 3, Format 335 may also specifyan algorithm or general pattern. Semantics 320 may be a class thatrepresents the semantics of the big data. Semantic 320 may be ComposedOf 330 Key/Value Pair 340, 345, which may be a class or object whichhelps to decipher the meaning of the big data based on key/value ofcertain information. Semantic 320 may also be Composed Of 330 Index 350.Index 350 may be a class or object that points to a specific meaning forthe purposes of semantic look ups.

Meta Data Information

Typically, conventional techniques have used Massive Parallel Processing(MPP) and Hadoop type technologies to process and transform informationand Big Data that is not structured into structured information.Generally, however, this requires the unstructured data to be forcedinto a tabular (table oriented) representation of the data. For examplerefer to FIG. 4. Generally, unstructured data 405 would be categorizedvia a tool, such as MPP 410 to unstructured and structured data 415.This data would have analytics performed on it by an analytics tool 420and be transformed to structured data 425, losing some of the fidelityof the data.

In certain embodiments, the current disclosure enables modeling andanalysis of structured, semi-structured, unstructured andmulti-structured information. In some embodiments, an abstraction layerlay may be created which may consist of a graph of “marks” that point topieces of information in the world, structured or otherwise. In certainembodiments, these “marks” represent topics or information of interestthat may be contained in the world and may point to where those pointsof interest can be found in the world. In further embodiments, thesemarks may group related pieces of “data” in the Big Data world providingSemantics information on the content of this information.

For example, refer to the example embodiment of FIG. 5. Unstructureddata 510 and structured data 520 may be used and mapped by MPP 530 intoorganized data 535, which may provide a mapping and means of access toboth the structured and unstructured data. In some embodiments, theorganization may provide not only accessed to the structured data thatmay be lost if storing it as structured data, but also may providefurther mappings or analytical information about the data.

In at least some embodiments, analytics may not be performed on theentire content of the Big Data World, instead, each “project” or set ofanalysis may have a “Context.” In some embodiments, the contest mayconsist of a set of “key words” or “topics” which may be referred to as“marks.” In most embodiments, each project or set of analytics to beperformed on the project such “finding”, “accessing”, “analyzing”, etc(e.g., counting, understanding, comparing), may be represented thepresence or not of these marks.

In some embodiments, within a context, these marks may searched for andanalyzed multiple times and information for these marks, their presenceand location should not be deleted, and instead may be maintained in afast memory to enable this information to be readily available. In someembodiments, this abstraction layer may not be independent of theunderlying Information System (e.g., File system, object store,database, etc.) rather it may provide a map to this information. Incertain embodiments, the layer of abstraction may be a way of organizinginformation that may be scattered across multiple file systems.

In further embodiments, once the marks are created much of the analyticsof the data set may be performed on the marks without accessing theunderlying data set. In certain embodiments, if the underlying datasetchanges, the marks indexes may need to be updated. In most embodiments,different marks may be created for different analytics and the marks maybe specific to the information needed to be examined by a user of thedataset.

In some embodiments, a project may define additional marks to beidentified and searched for in the data. In certain embodiments, aproject may find information in the data that goes beyond theinformation captured on a mark. In a particular embodiment, marks mayrepresent intermediate results on computations and point to informationwhere the intermediate result was obtained. In another embodiment, forexample when analyzing a Genome and counting the presence of a“repeatable” string, a mark may be a pair <“string”, “number ofoccurrences”> and may point to files and the location where that“string” had been found a certain “number of occurrences.” In thisembodiment, when a processing activity is executed to count that string,the activity may find each occurrence and may have to traverse theentire string. In this embodiment, the process may find and counts and“knows” where each “string’ is.

For example refer to the example embodiment of FIGS. 6 and 7. Inintelligent marker miner (iMM) Plane 700, there are two user markerpairs in which user 702 is connected to marker 704 and marker 706. Aswell, User 710 is connected to marker 708 and marker 712. These usermarker pairs represent views for each user into the underlying datathrough the use of a metadata map. In this embodiment, Marker 708 islinked to file 758 in File plane 720, which is linked to Block 780 inthe Block Plane. Marker 708 is also linked to Directory 736, which islinked to Object store (OStore) 760 and OStore 762 in the object storeplane, where OStore 760 is linked to block 782 in the Block Plane.

The example embodiment of FIG. 7 may be created by determining thestorage systems in the block plane 770 on which the data resides (step610). The file systems in the information plane may be determined (step615). The file system information in the file plane 745 may be gathered(step 620). The gathered data may be optimized (Step 625). Markers 704,706, 708, 710, and 712 may be created based on the data (step 630).FIGS. 6 and 7 represent example embodiments of how a metadata graph maybe created to represent how data for a particular user may be mapped toa subset of the data.

Refer now to the example embodiments of FIGS. 8 and 9. The Big Data 910may be chosen (step 810). The file system information 920 may beoptimized by region, domain, and other functions (step 815). The markers925, 930 may be implemented (step 820). The iMM model 915 may bepopulated with data from the File systems 920 (step 825). The model maybe checked for consistency (step 835). The model may be monitored (step830).

In certain embodiments, an abstract representation/model of anInformation System may be created using markers and connections betweenthe markers, markers and data. In some embodiments, the markers maycapture properties of data, including, but not limited to administrativeproperties, contextual properties, and semantic properties of the data.This modeled representation may be used as a means to organize andmanage data, including, but not limited to the whole structure of thefile system (directories and sub-directories), the abstraction of files,and the content stored within the file.

In further embodiments, DRAM and Flash may be leveraged to maintain ametadata representation in memory for fast access. In other embodiments,maintaining the representation/model may enable greater scalability asless information is stored, faster access as information is alreadyorganized, dynamic model representation changes, and in real time,enabling multiple marker-models to co-exist simultaneously, and enablingorganizational marker-models that are meshed (cyclical) not justhierarchical. In some embodiments, marker models may be dynamicallyextended/changed to capture more abstractions of interest. In mostembodiments, the representation may be file system “agnostic” and mayhide the details of the underlying file system.

In further embodiments, the representation may serve as an integrationto multiple file systems. In some embodiments, the representation may bea file system of file systems. In certain embodiments, one of the filesystems may be in the cloud.

In certain embodiments, administrative tasks may be performed by thenative file systems. In other embodiments, the representation may notallow writing of the actual files. In some embodiments, therepresentation may not remove the files. In other embodiments, abstractrepresentations may be updated dynamically and in real time.

In certain embodiments, analysis may be performed on the abstract modelor metadata. In certain embodiments, semantic and contextual informationthrough may be inferred through relationship/link traversal. In otherembodiments, capacity planning may be performed. In further embodiments,usage of space based on content creation rate per application/user/timeof the day may be estimated. In other embodiments, statistics onproperties of the files may be calculated.

In further embodiments, an abstract model may be used to represent andenforce Security constraints on operations to the files. In someembodiments, the model may be used to control access to content, accessto abstract representations, control the ability to create, update, anperform analysis on the abstract representation. In some embodiments,the abstract model may keep pointers to specific locations in the filewhere “relevant” content can be found, e.g. <Keyword>, <Block-Address,Byte-Number>. In at least some embodiments, connections may be createdeither manually or automatically, while others may be “inferred”manually or automatically, based on other existing connections.

In other embodiment, an abstract model representation may used to linkmultiple different Big Data models. In most embodiments, connectionsbetween systems may not be multi-exclusive. In certain embodiments,there may be as many connections as necessary and the connections comingout of relations may not need to be to the same “type” of entity. Infurther embodiments, the same entity in the abstract model may connectto a file system, a sub-directory and a block all at the same time. Inalternative embodiments, the abstract model may be tied to one or moreof the following: File System, Virtual File System, Object Store,Virtual Object Store, Directory or sub-directory, File, Block, VirtualBlock.

In certain embodiments, an implementation of an abstract models may bepersisted in permanent storage so that the model need not be calculatedeach time it is to be analyzed. In other embodiments, as the modelchanges, the previous model may be stored to analyze changes to themodel over time. In some embodiments, aspect of the model may beanalyzed by outside tools such as EMC's GreenPlum. In furtherembodiments, multiple user views may be created, where different usersmay access different perspectives/views of the abstract model based oninterest and areas of focus. In certain embodiments, different views maybe accessed based on Viewers interest and security permissions. Infurther embodiments, depending on the user/view combination a subset ofthe abstract model may need to be up loaded into main memory. In stillfurther embodiments, multiple views may be maintained simultaneously forthe same or multiple users.

In a particular embodiment, an abstract model representation may be usedas “meta information” for the underlying File System to enable“management” or “organization” of the underlying files in a moreoptimized manner. In this embodiment, files/blocks with multipleconnections to the abstract model may be spread across the storagearrays and may reside in the lower storage tiers, and a higherconnection index may indicate a higher probability of access.

In some embodiments, short-cuts may be created to represent thedependencies between keys (a type of a Mark) and the data to which theyare related. In other embodiments, persistent storage for Key-Valuepairs/map function may be provided locally in nodes and globally foradditional processing/visualization. In some embodiments, simultaneousview and analytics of the same data may be available from differentperspectives. In further embodiments, the abstract model may be used asa visualization tool to graphically present the data and relationsbetween the data.

Refer now to the example embodiment of FIG. 10. FIG. 10 represents asample model that may be used to model the maker information. Data 1005contains information systems 1035, File systems 1040, Blocks, 1045,Object Store 1050, Database System 1055, and Object 1060 and is mappedinto 1062 SNIA 1065. The data is marked 1007 by Marked Cluster 1025which is make up of markers such as marker 1030. Markers may be accessed1012 by users, such as user 1010, where each user may embody 1017 aperson 1015 and a assume 1022 a role 1020.

Refer now to the example embodiment of FIG. 11. Data 1105 is mapped frominformation systems 1135. The data in information systems 1135 is mappedto addresses 1110, blocks 1145, File systems, 1140, object store 1010,database systems 1155, objection 1160, and Directory 1115. Directory1115 is mapped to SNIA object 1185. Objection 1160 is mapped to SNIAobject 1180. Database system 1155 is mapped to SNIA DBS 1178. ObjectStore 1150 is mapped to SNIA OS 1175. File system 1140 is mapped intoSNIA FS 1170. Block 1145 is mapped into SNIA Block 1168. Address 1110 ismapped into SNIA Object 1165.

Refer now to FIG. 12, which represents an example embodiment of dividingthe data into markers. Marker cluster 1210, consisting of marks 1215,marks data 1205. The marker cluster has a set of markers 1230. The marksmay be administration marks 1217, contextual markers, 1220, orsemantical markers.

Refer now to the example embodiment of FIG. 13. User 1310 is embodied byperson 1320 and assumes role 1325. User 1310 accesses marker cluster1315 which is made up of marker 1330 and marks data 1305.

Refer now to the example embodiment of FIG. 14. File systems 1465 hasfile system 1435 and directory 1440, file 1445 and block 1450. Markers1425 and 1430 are mapped to directory 1440 and block 1450 respectively.User 1420 is mapped to marker 1425 and marker 1430. User 1420, Marker1425 and Marker 1430 are in the IMM domain 1460. The IMM domain 1460 ismapped to a contextual semantic domain 1455. Domain 1455 has researcher1405 which is mapped to user 1420. Researcher 1405 is also mapped togrant 1410, which is in turn mapped to marker 1425. Grant 1410 is mappedto project 1415, which is mapped to marker 1430.

Refer now to the example embodiment of FIG. 15. In FIG. 15Bioinformatics project 1510 is run by business unit 1515 and issupported by IT 1540. Bioinformatics project 1510 is part oforganization 1 and has grants managed at finance 1520. Organization 1has function 1520 and is supported by support 1525. Organization 1 isalso connected to finance 1530. Business unit 1515 is also connected toIT 1540.

Refer now to the example embodiment of FIG. 15. Bioinformatics project1610 is related to Business Unit 1, IT 1620 and Finance 1625. Businessunit 1615 is optimized by Business User 1630, which consists of Manager1635 and Engineer 1640. Manager 1635 is Jill 1645. Engineer 1640 is Jack1650. Jack 1650 is connected to Jill 1645 over a social network. IT 1620has IT user 1655 which is connected to IT expert 1660, which is David1665 who is connected via a social network to Jill 1645. Finance 1625 ismade up of It user 1670, who is analyst 1675, who is mike 1680. Mike1680 is connected to Jill 1645.

Refer now to the example embodiment of FIG. 17. Bioinformatics project1710 is composed of business unit 1715, IT 1720, and Finance 1730. Jack1735 and Jill 1740 make up business unit 1715. David 1745 makes up IT1720 and Mike 1750 makes up finance 1730. Maker 1755 marks Jill tomarker 1 which marks files systems 1770 and 1775. Marker 1755 marks datato marker 1760, which marks file system 1780. Marker 1675 connects Mike1750 to File system 1785.

Refer now to the example embodiment of FIG. 18. Bioinformatics project1805 has marker 1810, marker 1820, and marker 1825. Marker 1810 marksFile systems 1830 and 1835. File system 1830 has file system summary1840 and file system 1835 has file system summary 1845. File systemsummary has attributes 1870, billing data 1875, block data 1877, filesdata 1880, and zones data 1885. Marker 1820 marks file system 1850 whichhas summary 1885. Summary 1885 has attributes 1890. Marker 1825 marksfile system 1860. File system 1860 has file system summary 1865. Filesystem summary 1865 has file system attributes 1895.

Refer now to the example embodiment of FIG. 19 outlining a markercluster for Parkinson's disease. Marker cluster 1910 has marker 1920 andmarker 1915. Marker 1920 has file system attributes 1925, billing data1930, blocks data 1935, file data 1940, and zones data 1945.

Genome Indexing

In certain embodiments, the current techniques may be used to generatean index or one or more index planes for Big Data information. In someembodiments, this index may be used to distribute the Big Data to nodesfor analysis. In certain embodiments, the nodes may be those of a Hadooptype architecture. In further embodiments, several index planes may begenerated. In still further embodiments, each index plane may berepresented at a different level of abstraction and may created meshedplanes of abstraction. In a particular embodiment, a plane ofabstraction or index plan may be hierarchical. In other embodiments, theplane of abstraction may be cyclical. In most embodiments, the indexplane or index planes may be used to distribute Big Data to the nodes.In further embodiments, map reduce algorithms may be applied to performnext generation sequencing analysis. In still further embodiments, theindex plane may be a pre-reduce algorithm applied before a map-reducealgorithm to distribute Big data to processing nodes.

In some embodiments, the index plane may be used to aggregate and storeinformation and analysis returned by the analysis nodes. In certainembodiments, the information in the index plane may be stored in aquickly accessible medium, which may enable requested information to beaccessed by examining the information stored in the index plane insteadof accessing the underlying data.

In some embodiments, techniques of the current disclosure may be appliedto any indexing system. In certain embodiments, some of the techniquesmay be applied to the performance of in-memory analytics to createindices and to store indices. In further embodiments, the analytics mayperformed and stored at the index level In these embodiments, the actualindexed elements may reside in storage while the indexes may residein-memory. In other embodiments, data may be brought from storage intomain or quickly accessible memory based on number of indices pointing tothe data. In some embodiments, the data may be stored in a low latencystorage medium. In certain embodiments, the low latency storage mediummay be flash ram or DRAM. In further embodiments, the low latencystorage medium may enable a matrix type instant access mode forstructured, unstructured and multi-structured data. In still furtherembodiments, the low latency storage medium may avoid cylindricalstorage access times associated with a spinning storage medium.

In certain embodiments, the index planes may be located in a quicklyaccessible medium such as flash or DRAM. For example refer to theexample embodiment to of FIG. 20. FIG. 20 illustrates some examplemetrics for different types of storage mediums. For example, the latency2060 for DRAM 2010 is 0.005 microseconds. Conversely, the latency 2060for HDD 2030 is 7-12 milliseconds. This chart illustrates severalexamples of how the use of different storage mediums can impact theaccess speed of information.

Refer now to the example embodiment of FIG. 21. In this exampleembodiment, there are two index planes, 2120 and 2145, and a generationplane 2175. In this embodiment, the index planes map information ontothe generation plane to enable information to be distributed to andcomputed by processing nodes. For example indices 2125 and 2130 may togeneration 2145. Index 2105 maps to index 2125 and index 2110 maps togeneration 2155.

Consider the example embodiment of FIG. 21 in reference to a Big Dataset consisting of a set of genomic markers upon which analysis may beperformed. In certain embodiments, there may be a set of sequences. Insome embodiments, each sequence may be in a file and each sequence maybe stored in a node. In some embodiments, the analysis may result in asequence of indices in a format of keypairs upon which analysis can beperformed. In some embodiments, it may be desired to understand whatother sequences are 1-letter aligned at position1. In other embodiments,it may be desirable to determine what other sequences are 2-letteraligned at position1. In further embodiments, it may be desirable todetermine what other sequences are 2-letter aligned at position2. Incertain embodiments, the genome sequencing may be organized intokey-value pairs. In some embodiments, the key may be a<letter-sequence,starting-position>pair and the value may be aValue=<SequenceId>. In other embodiments, several indices may be createdsuch as one for 1-letter and another for 2-letter sub-sequence. Infurther embodiments, it may be desired to determine how may pairs have aparticular combination, such as <C,1>. In other embodiments, it may bedesired to query how many pairs have a <CA,1> pair.

For example, refer to the example embodiment of FIG. 22. A collection ofsequences may be inputted and each sequence may be in a file, and eachfile divided into segments, where each segment stored on a node (step2210). A sequence of indexes in the format of key-value pairs may beoutputted where a key is a <letter-sequence,starting-position> and avalue is a <SequenceId> (step 2220). The extracted sub sequences may bemapped to create key-value pairs (step 2230). Duplicated in the data maybe reduced (step 2340). An optimal way to distribute the data may bedetermined (step 2350). In certain embodiments the data may bereplicated. The index data distributed across the nodes may be inputted(step 2360). The results of the query may be outputted (step 2370).

Refer now to the example embodiments of FIGS. 23 and 24. TheBioInformatics Big Data Storage may be started. The BioInformatics datamarkers, CAT 2320, GAT 2320, and TAC, 2340 may be gathered (step 2410).The genomics data for the search may be gathered (step 2420). TheBigData search may be mapped on to markers (step 2430). The results ofthe mapping, such as shown in FIG. 23, may be gathered (step 2440).

Refer now to the example embodiment of FIG. 24. The genomics BigData andmarkers may be selected (step 2510). The genomics search patterns may bechosen gathered (step 2520). The marker indicates may be searched (step2530). The Big Data set may be searched (step 2540). The search resultsmay be reported (step 2550). The data consistency may be checked (Step2560).

In certain embodiments, there may be different genome sequences ofdifferent length and makeup. In some embodiments, the sequences may becategorized into word sequences, sentence sequences, which may be acombination of word sequences, or in definite sequences which may be aset of indefinite sequences. In further embodiments, the set of wordsequences may be indexed across several index planes. In certainembodiments, this information may be stored in an index construct. Infurther embodiments, the index construct may be stored in highlyaccessible low latency storage. In still further embodiments, the BigData may be searched by accessing the index construct without accessingthe underlying Big Data. In a particular embodiment, the exampleembodiment of FIG. 21 may represent index planes and the exampleembodiment of FIG. 23 may represent the index construct.

The methods and apparatus of this invention may take the form, at leastpartially, of program code (i.e., instructions) embodied in tangiblemedia, such as floppy diskettes, CD-ROMs, hard drives, random access orread only-memory, or any other machine-readable storage medium. When theprogram code is loaded into and executed by a machine, such as thecomputer of FIG. 26, the machine becomes an apparatus for practicing theinvention. When implemented on one or more general-purpose processors,the program code combines with such a processor 2603 to provide a uniqueapparatus that operates analogously to specific logic circuits. As sucha general purpose digital machine can be transformed into a specialpurpose digital machine. FIG. 27 shows Program Logic 2734 embodied on acomputer-readable medium 2730 as shown, and wherein the Logic is encodedin computer-executable code configured for carrying out the reservationservice process of this invention and thereby forming a Computer ProgramProduct 2700. The logic 2734 may be the same logic 2640 on memory 2604loaded on processor 2603. The program logic may also be embodied insoftware modules, as modules, or as hardware modules.

The logic for carrying out the method may be embodied as part of thesystem described below, which is useful for carrying out a methoddescribed with reference to embodiments shown in, for example, FIG. 24and FIG. 25. For purposes of illustrating the present invention, theinvention is described as embodied in a specific configuration and usingspecial logical arrangements, but one skilled in the art will appreciatethat the device is not limited to the specific configuration but ratheronly by the claims included with this specification.

Although the foregoing invention has been described in some detail forpurposes of clarity of understanding, it will be apparent that certainchanges and modifications may be practiced within the scope of theappended claims. Accordingly, the present implementations are to beconsidered as illustrative and not restrictive, and the invention is notto be limited to the details given herein, but may be modified withinthe scope and equivalents of the appended claims.

What is claimed is:
 1. A computer implemented method for modeling a BigData dataset, the method comprising: creating non-specificrepresentations of the Big Data dataset by representing, as objects in acomputer model, non-specific representations including metaInformation,DataSet, BigData and Properties representations; wherein thenon-specific representations of the Big Data dataset enablesrepresentation of unstructured big data, structured big data, and bigdata including unstructured big data and structured big data; creatingnon-specific representations of mapping of the Big Data by representing,as objects in a computer model, non-specific representations includingUser representations and marker representations, wherein each of theuser representations includes one or more views of the Big Data datasetcomprised of one or more of the marker representations, wherein eachview shows a perspective of the Big Data dataset, wherein at least oneof the one or more views of the Big Data dataset is enabled to representan abstraction of the Big Data dataset, wherein the abstraction of theBig Data dataset is enabled to be metadata for mapping the informationin the Big Data dataset; where the user representations are mapped toone or more marker representations and the marker representations arematched to one or more elements of the Big Data dataset; and creatingnon-specific representations of marker clusters, as objects in acomputer model; wherein a marker cluster includes a set of markers;wherein a marker includes of a set of marks; where a mark is a propertyof data of the big dataset; wherein a marker is enabled to mark data ina file system plane, an object plane, and a block plane.
 2. The methodof claim 1 wherein the file system plane includes one or more filesystems, wherein an object plane includes one or more object stores,wherein a block plane includes one or more block stores.
 3. The methodof claim 1 further comprising: creating non-specific representations ofmarks, as objects in a computer model, as non-specific representationscomprising administration properties, contextual properties, andsemantical properties.
 4. The method of claim 3 wherein the userrepresentations embodiments a person and the user representations assumea role property.
 5. The method of claim 4 further comprising: mapping acontextual semantic domain to the users and markers.
 6. The method ofclaim 1 wherein model enables a IT organization to charge back cost to abusiness unit that accesses the Big Data set.
 7. The method of claim 1wherein the model is stored in a low latency storage medium.
 8. Acomputer program product for use in replication comprising: anon-transitory computer readable medium encoded with computer executableprogram code for migration of data, the code configured to enable theexecution of: creating non-specific representations of the Big Datadataset by representing, as objects in a computer model, non-specificrepresentations including metaInformation, DataSet, BigData andProperties representations; wherein the non-specific representations ofthe Big Data dataset enables representation of unstructured big data,structured big data, and Big Data including unstructured big data andstructured big data; creating non-specific representations of mapping ofthe Big Data by representing, as objects in a computer model,non-specific representations including User representations and markerrepresentations, wherein each of the user representations includes oneor more views of the Big Data dataset comprised of one or more of themarker representations, wherein each view shows a perspective of the BigData dataset, wherein at least one of the one or more views of the BigData dataset is enabled to represent an abstraction of the Big Datadataset, wherein the abstraction of the Big Data dataset is enabled tobe metadata for mapping the information in the Big Data dataset; wherethe user representations are mapped to one or more markerrepresentations and the marker representations are matched to one ormore elements of the Big Data dataset; and creating non-specificrepresentations of marker clusters, as objects in a computer modelwherein a marker cluster includes a set of markers; wherein a markerincludes of a set of marks; where a mark is a property of data of thebig dataset; wherein a marker is enabled to mark data in a file systemplane, an object plane, and a block plane.
 9. The program product ofclaim 8 wherein the markers include contextual markers, semanticalmarkers, and administration markers.
 10. The program product of claim 8wherein the executable program code is further configured for executionof: creating non-specific representations of marks, as objects in acomputer model, as non-specific representations comprisingadministration properties, contextual properties, and semanticalproperties.
 11. The method of claim 10 wherein the user representationsembodiments a person and the user representations assume a roleproperty.
 12. The program product of claim 11 wherein the executableprogram code is further configured for execution of: mapping acontextual semantic domain to the users and markers; wherein the filesystem plane includes one or more file systems, wherein an object planeincludes one or more object stores, wherein a block plane includes oneor more block stores.
 13. The program product of claim 11 wherein themodel enables a IT organization to charge back cost to a business unitthat accesses the Big Data set.
 14. The program product of claim 11wherein the model is stored in a low latency storage medium.
 15. Anapparatus comprising: a processor and memory storing instructions that,when executed on the processor, cause the apparatus to: create, at afirst module, non-specific representations of the Big Data dataset byrepresenting, as objects in a computer model, non-specificrepresentations including metaInformation, DataSet, BigData andProperties representations; wherein the non-specific representations ofthe Big Data dataset enables representation of unstructured big data,structured big data, and Big Data including unstructured big data andstructured big data; create, at a second module, non-specificrepresentations of mapping of the Big Data by representing, as objectsin a computer model, non-specific representations including Userrepresentations and marker representations, wherein each of the userrepresentations includes one or more views of the Big Data datasetcomprised of one or more of the marker representations, wherein eachview shows a perspective of the Big Data dataset, wherein at least oneof the one or more views of the Big Data dataset is enabled to representan abstraction of the Big Data dataset, wherein the abstraction of theBig Data dataset is enabled to be metadata for mapping the informationin the Big Data dataset; where the user representations are mapped toone or more marker representations and the marker representations arematched to one or more elements of the Big Data dataset; and create, ata third module, non-specific representations of marker clusters, asobjects in a computer model; wherein a marker cluster includes a set ofmarkers; wherein a marker includes of a set of marks; where a mark is aproperty of data of the big dataset; wherein a marker is enabled to markdata in a file system plane, an object plane, and a block plane.
 16. Theapparatus of claim 15 wherein the markers include contextual markers,semantical markers, and administration markers.
 17. The apparatus ofclaim 15, wherein the instructions that, when executed on the processor,further cause the apparatus to: create, at a fourth module, non-specificrepresentations of marks, as objects in a computer model, asnon-specific representations comprising administration properties,contextual properties, and semantical properties.
 18. The apparatus ofclaim 17 wherein the user representations embodiments a person and theuser representations assume a role property.
 19. The apparatus of claim18, wherein the instructions that, when executed on the processor,further cause the apparatus to: map a contextual semantic domain to theusers and markers; wherein the file system plane includes one or morefile systems, wherein an object plane includes one or more objectstores, wherein a block plane includes one or more block stores.
 20. Theapparatus of claim 15 wherein model enables a IT organization to chargeback cost to a business unit that accesses the Big Data set.
 21. Thecomputer implemented method of claim 2 wherein user representationconnection to a marker denotes security and access privileges of thatuser representation to the data associated with the markerrepresentation.
 22. The computer implemented method of claim 2 furthercomprising: determining storage systems in the block plane; determiningfile systems in the file system plane; and determining object stores inthe object plane.